home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group97a.txt
/
000105_icon-group-sender _Wed Apr 9 09:14:10 1997.msg
< prev
next >
Wrap
Text File
|
2000-09-20
|
1KB
|
32 lines
Message-Id: <199704091947.AA11216@cheltenham.cs.arizona.edu>
Received: by cheltenham.cs.arizona.edu; Wed, 9 Apr 1997 12:47:37 MST
Date: Wed, 9 Apr 97 17:09:32 BST
From: Jeff Dalton <jeff@aiai.ed.ac.uk>
Subject: Re: Problem with Icon 9.3
To: eka@corp.cirrus.com (Eka Laiman), ko@surya.ho.att.com (Kostas Oikonomou)
Cc: icon-group@cs.arizona.edu
Errors-To: icon-group-errors@cs.arizona.edu
Status: RO
Content-Length: 895
> Wow, indexing using "list"s?
>
> I do not know if ICON's tables are built with this kind of operation in
> mind. I personally think that ICON tables are like "hash table" where the
> indexing can be done using both "strings" or "integers". According to the
> definition: "Tables resemble lists, except that the keys, or 'subscripts',
> need not be integers but can be *values of any type*." I have not tried to
> do indexing based on "float" yet, although theoretically that's possible
> :-)
But doesn't "list" fall under "any type".
Hash tables in Common Lisp can be indexed by lists. (How it
depends on the "test" specified when the table is created. For
a table where the test is "equal", the contents of the list matter.
For one there the test is "eql" (which is pretty close to identity),
only the "address" of the lisyt would be used. A similar rule applies
to strings.)
-- jeff